feat(collections): standardize maturity field across all 14 collection YAML manifests#1432
Draft
MauroDruwel wants to merge 1 commit intomicrosoft:mainfrom
Draft
Conversation
…n manifests (microsoft#1319) - Add collection-level maturity: field to 11 collection YAMLs that were missing it - Move maturity: field in design-thinking.collection.yml to consistent position after description: - Placement is after description: and before notice:/tags:/items: across all manifests Proposed maturity assignments (Docusaurus as source of truth): - ado, coding-standards, data-science, github, hve-core, hve-core-all, installer, project-planning: stable - design-thinking: preview (already set, position corrected) - experimental, gitlab, jira, rai-planning, security: experimental Note on coding-standards, data-science, project-planning: Docusaurus assigns these as Stable at the collection level even though individual plugin items carry experimental maturity. Collection maturity represents the collection's distribution readiness, not the stability of every individual artifact it contains. Note on hve-core-all, installer: not in Docusaurus; both wrap stable packaging so stable is the appropriate default. - Update Validate-Collections.ps1 to enforce maturity: presence as a required field (previously optional — missing values passed silently) - Update Validate-Collections.Tests.ps1: change "Passes validation for collection with omitted maturity" to "Fails validation for collection with omitted maturity" and add maturity: stable to all other test manifests that were created without it Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #1319
Audited all 14 collection YAML manifests against
docs/docusaurus/src/data/collectionCards.tsand resolved every gap, conflict, and placement inconsistency identified in the issue.Changes
1. Collection YAML manifests — maturity field added/corrected
maturity:is now placed consistently afterdescription:across all 14 manifests.adostablecoding-standardsstabledata-sciencestabledesign-thinkingpreview(wrong position — after tags)preview(after description)experimentalexperimental✓githubstablegitlabexperimentalhve-corestablehve-core-allstableinstallerstablejiraexperimentalproject-planningstablerai-planningexperimental✓securityexperimental2.
Validate-Collections.ps1— maturity is now requiredChanged
maturity:from an optional field (silently passes if absent) to a required field. Before: the validator only checked values when the field was present. After: missingmaturity:field triggers a validation error with messagemissing required field 'maturity'.The new check follows the same pattern as other field validations (id, name, description) and uses the existing
$allowedMaturitiesset:stable,preview,experimental,deprecated.3.
Validate-Collections.Tests.ps1— tests updated for new behaviormaturity = 'stable'to all other test manifests that were constructed without a maturity field (these tests were verifying unrelated behavior — path validation, folder naming, marker parsing — and needed the field to satisfy the new requirement).Conflict Resolution: Collection Maturity vs. Plugin-Item Maturity
Three collections (
coding-standards,data-science,project-planning) showexperimentalat the plugin-item level butStablein Docusaurus. This PR sets collection-level maturity tostablematching Docusaurus, for the following reason:Meta-Collection Decision
hve-core-allandinstallerare not present in Docusaurus. Both are packaging meta-collections wrapping stable production content, sostableis the correct value.Testing
npm run lint:collections-metadatanpm run test:ps -- -TestPath scripts/tests/collections/npm run plugin:generateManual testing was not performed.